← Back to issue list

Linter is checking against host libs when using --build-for argument

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1996206
Type
issue
State
open
Author
~dbruno74
Labels
Created
2022-11-10 15:57:49.573955+00:00
Updated
2022-11-10 15:58:38.294734+00:00
Closed

Current evaluation

No evaluation has been recorded for this issue yet.

Issue body

Linter (for libraries) is looking for dependencies on core snap lib of the host architecture instead of the target specified in --build-for. This is evident from the trace below, where when checking dependencies of an aarch64 shared object (MAC-IS.so) the LD_LIBRARY_PATH variable looks into /snap/core22/current/lib/x86_64-linux-gnu (and fails). 2022-11-10 15:18:51.725 executing: LD_TRACE_LOADED_OBJECTS=1 LD_LIBRARY_PATH=/root/prime/lib:/root/prime/usr/lib:/snap/core22/current/lib:/snap/core22/current/usr/lib:/snap/core22/current/lib/x86_64-linux-gnu:/snap/core22/current/usr/lib/x86_64-linux-gnu usr/lib/aarch64-linux-gnu/gconv/MAC-IS.so 2022-11-10 15:18:51.734 Unable to determine library dependencies for 'usr/lib/aarch64-linux-gnu/gconv/MAC-IS.so' The following trace has been generated with a part including coreutils:arm64 as stage-packages and building on an x86_64 machine with: snapcraft --build-for=arm64

Evaluation history

No evaluation history available.